Cream of the Crop 25

home *** CD-ROM | disk | FTP | other *** search

/ Cream of the Crop 25 / Cream of the Crop 25.iso / bbs / dizl140.zip / DIZL.DOC < prev next >

Wrap

Text File | 1997-05-09 | 45KB | 860 lines

┌─────────────────────────────────────────────────────────────────────────────┐ │ The DiZList v1.4 Mind Over Byte Software 1997 Copyright All rights reserved │ └─────────────────────────────────────────────────────────────────────────────┘ M A I N D O C U M E N T A T I O N ▄██▄ ▄██▄ ▄█▄ ▄██▄ ▄██▄ ▄████████▄ █████▄█████ █████ █████▄ ████ ████ ▀███ ███████████ █████ ███████████ ████ ███ ████ ▀ ████ █████ ████▀██████ ████ ███ ████ ████ █████ ████ ▀████ ████▄▄▄███▀ ▀██▀▀▀▀▀▀█▀ ▀▀█▀ ▀▀▀▀▀▀▀▀▀▀▀ ▀▀▀▀▀▀██▀ ▀▀ ▀▀ ▀▀ ▀▀ ▀▀ ▀▀ ▀▀ ▀▀▀ ▀▀▀ ▀▀ ▀▀ ▀▀▀▀▀ ▀▀▀▀▀▀ ▀▀ ▀▀ ▀▀▀ ▀▀ ▀▀ ▀▀ ▀▀▀▀▀ ▀ ▀▀▀▀▀▀▀ ▀▀ ▀▀ ░░ ░░ ░░ ░░ ░░ ░░ ▒▒▒▒▒▒ ▒▒▒▒ ▒▒ ▒▒▒▒▒ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ██████ ██ ██ ██████ S O F T W A R E (tm) ┌─ Mind Over Byte Software ─┐ Owner : Mark Bloss │ T h e D i Z L i s t │ │ Evaluation Edition │ Fido 1:116/180 └───────────────────────────┘ A SPYER BBS (615)831-9284 Mind Over Byte Software ┌─── GUARANTEE ────┐ PO BOX 112015 └─────License──────┘ Nashville Tennessee 37222 There is no guarantee as to the usefulness or fitness of this program for use on your system. The author, distributors, agents or others from whom you received this program cannot be held liable for any damages to your system connected with this program or accompanying documentation. You use this program at your own risk. Mind Over Byte Software, and A Spyer BBS, are owned and operated by Mark Bloss. All Archiver Programs have copyrights held by their respective authors and/or representatives. See Acknowledgements at the end of this document for copyright notices, etc. ++001++ ┌──────────────────────────────────────────────────────────────────────┐ │ PROGRAM USE ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────┘ Congratulations! You have just acquired the best list-maker program available today. The DiZList is a List Maker for Archive libraries. It can create lists in order by Filename, and/or by Areaname which you configure. It can use descriptions from other sources, other than Internal Description files (FILE_ID.DIZ, VENDINFO.DIZ, DESC.SDI, SDN.ID), such as FILES.BBS and/or 4DOS (or NDOS) "DESCRIPT.ION" files. The DiZList will allow you to import descriptions found from these Alternate Sources into their associated archives as well. The lists themselves can make use of several different STYLES, some of which were created by the fine Beta Team of The DiZList. It allows you to create your own Header and Footer files for each individual list you configure. And because DIZL depends on a separate configuration for each list you create, the number of different lists are effectively limitless. The DiZList will take a LOT of time to run the first time it is run, because it is building a database using internal description files, and this can be very time-consuming. After that - the database is used instead, and the same archives are never touched again (unless you tell DIZL to do so). New additions are added, and archives that disappear are automatically removed at a preset (and configurable) time. The databases for The DiZList will be large if you have a large number of files, and this is unavoidable, but a by-product of the disk storage is reliable and fast service during nightly events, and attractive and varied lists which have many features you won't find in any other list-maker program in the world. If you use a Magic-name file, Magic names can be annotated in every list created, and a separate Magic "Mini-List" can be created as well. The DiZList fully supports ARC, ARJ, RAR, SQZ, ZIP, ZOO and LZH archives. You only need two for The DiZList to work. The DiZList may be configured to exclude files by extension, create downloadable archives of your lists, and handle CD-ROM disks. The DiZList (DIZL) will use EMS and/or XMS memory if you have it. It does its best to use Conventional memory economically and has fewest problems with a free system running under straight DOS or virtual 8086 mode at protection level 0. See the section labeled SYSTEM REQUIRMENTS below for more technical information. ┌──────────────────────────────────────────────────────────────────────┐ │ FIRST EXECUTION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────┘ You will need to configure your Initialization file(s) before running DIZL the first time. If you are just starting out, run the INSTALL program first, and answer (Y)es when it is done to start DZSETUP. If you need to run DZSETUP later, and do not have an *.INI file in the home directory, key in DZSETUP DIZLIST <enter>. This will create the default Initialization file for you when you save your changes before ending the program. On the initial run of DIZL.EXE, the program must build a database. If you include a large enough sample of directories, DIZL may run for quite some time. This is characteristic of the first-run of programs such as this. DIZL is also unable to work around bad archives, if the external archive program finds it invalid. This might cause DIZL.EXE to hang; and the only solution is to get rid of the offending archive. If you have several invalid archives such as this: DIZL will offer a unique opportunity for you to weed them out. My apologies in advance for this inconvenience, but the result will be worth the trouble. ┌──────────────────────────────────────────────────────────────────────┐ │ INSTALLATION/UPGRADING ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────┘ An installation program accompanies the main archive. Simply run INSTALL to install The DiZList for the first time OR if upgrading from a previous version of the program. The INSTALL.EXE program will update your current datafiles and initialization files automatically whenever it is required - provided you are upgrading from the previous released version. If you are upgrading from a version prior to the previous release there may be other requirments; see UPDATE.vn There are no environment variables needed, and no changes must be made to your start-up files (AUTOEXEC.BAT, CONFIG.SYS etc). You may run DIZL from anywhere and do not have to Change to the Home Directory to run it, even if DIZL is not in your PATH. Simply use a fully-qualified path when executing it. (Example: E:\UTILS\DIZL\DIZL) You should, however, log to the Home Directory whenever you run the DZSETUP.EXE program. DIZL will create and use a sub-directory of your DIZL home directory called DATA, which will hold the database files for program use. In addition, DIZL will create and remove a work directory for its own use during program runs. You do not have to create these directories yourself, DIZL does all the work for you. The work directory is used when extracting internal description files from archives, and for a holding directory when archiving the downloadable list archive. It is also configurable, using the DZSETUP program, if you want to use a RAM drive instead. DZSETUP.EXE will allow you to view all the pertinent documentation files while you configure the program, it has menu-sensitive help available by pressing F1 at any time the program is not waiting for field-entry- input from you. CREATING AN INITIALIZATION FILE. To create the default initialization file, enter DZSETUP DIZLIST <enter> from the DOS prompt. You must be logged to the Home Directory first. When you need to create another initialization file (*.INI), include a name for it on the command-line, such as "DZSETUP GAMES". QEMM/DESQVIEW USERS: ** Please note that under Desqview, and only in "Big DOS", an error MAY occur during the INSTALL.EXE program. If you receive notification of the Exception #13 error, you do NOT have to reboot the machine. Simply switch to the smaller DOS partition (128k) and the Install will function normally, although much slower than when run from plain DOS. You should Zoom the window before starting the INSTALL program under Desqview. If you wish, you may want to drop out of Desqview for the Installation procedure. There will not be enough memory in the 128k DOS window to execute DZSETUP from the prompt at the end of the INSTALL program; instead you will need to run DZSETUP from the "Big DOS" partition due to greater memory requirments. No errors occured while testing all DIZL programs under QEMM without Desqview running. ┌──────────────────────────────────────────────────────────────────────┐ │ CONFIGURATION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────┘ ++002++ ┌─────────────────────────────┐ │ Logging │ └─────────────────────────────┘ DIZL will only keep a log file if you tell it you want one. You have the option to specify a different Logfile for each configuration or simply let DIZL use DIZL.LOG as the default. See "Logging Configuration" in DZSETUP. You can also have DIZL log your CONFIGURATION section for debug purposes. This option can be enabled/disabled in DZSETUP as well. ++003++ ┌─────────────────────────────┐ │ Work Directory │ └─────────────────────────────┘ This is the directory DIZL will use for extracting internal description files, and when creating downloadable archives for your lists. The default is created and removed each time DIZL runs, and is called DIZLWORK.TMP. If you install The DiZList in C:\DIZL\, then the work directory that is created, used during program runs, then removed at normal program termi- nation, would be C:\DIZL\DIZLWORK.TMP\. If DIZL should ever terminate with an error, this directory might be left behind. DIZL will properly handle this situation when run the next time. The Path Specification may be changed at the Miscellanea Menu in the Configuration program, if you would like to use a RAM drive instead. Please be aware that there should be sufficient space available to manage possibly several megabytes of data, allowing for the size of your list- file(s) before compression, any included files, and your own description files to add to any downloadable archives. Internal description files generally take less than 1k of disk-space and therefore would not be a consideration. ++004++ ┌──────────────────────────┐ │ Paths Configuration │ └──────────────────────────┘ These directories hold the archives you want listed in each of the various configurations. DZSETUP allows you to use several methods to import these directories without so much typing on your part. Area Names (titles) should be limited to 40 characters. These entries are the titles of each section placed in the lists themselves. When keying in pathnames, if it is found to be invalid you will hear an error beep. You must enter valid pathnames in this section. The Directory list is maintained in a separate configuration file called DIZLPTHS.CFG. After you have configured and saved this information in DZSETUP, the file will be in the DIZL home directory, and can be edited with a standard text editor. It will also include instructions to help you edit it should you have the need to. It can also be maintained completely and solely using DZSETUP. ++020++ ┌──────────────────────────┐ │ Sorting Area Names │ └──────────────────────────┘ The Area Names (titles) which you give to each path configured in the Paths Configuration, can be listed in each list in Configuration order, or can be sorted in alphabetical order by toggling Sort Areas ON in DZSETUP at the Toggles Menu. ++005++ ┌──────────────┐ │ List Types │ └──────────────┘ Two different sorts of list file can be created by DIZL in any of the configurations you create. The AREA List and the ALPHABETIC List. The Area list lists files by Area, naturally, and the Alphabetic List lists files in simple alphabetic sequence regardless of the Area. You can specify that DIZL create either one or both lists. Include the name you want these files to have in DZSETUP at List Configuration. ++006++ ┌─────────────────────────────┐ │ Header and Footer Files │ └─────────────────────────────┘ A header and footer file can be designed by you to make your list reflect your BBS or anything you like. If the program cannot find these files, it will use the internal plain-Jane header and footer. These are configured in DZSETUP at List Configuration. You may, of course, create more than one header and footer file to use with different configurations. UNREGISTERED USERS CANNOT CONFIGURE A FOOTER FILE, THE INTERNAL FOOTER IS USED INSTEAD. (**) ** Please note that DZSETUP will allow unregistered copies to be completely configured *as if* you owned a registered version. DIZL will ignore and use the default settings, or disable activated ones not allowed, until the program is registered. ++007++ ┌─────────────────────────────┐ │ Description Handling │ └─────────────────────────────┘ ARCHIVES/FILES WITH NO DESCRIPTION Files which do not have a description may be included or excluded from your lists. Setting this may be done in DZSETUP at the Description Handling Menu. If they are included, you may also update the phrase to use in the list, at that menu. If you have configured DIZL to include descriptions from Alternate sources, these sources are checked first before anything is left out. ++008++ ALTERNATE DESCRIPTIONS (REGISTERED USERS ONLY) When an archive does not have a valid description - you can specify what, if any, other source to use for descriptions. Choices are FBBS, NDOS or 4DOS, NONE, or ALL. To import descriptions for files without an internal description file, "Re-check Missing Descriptions" must be toggled on at the Description Handling menu in DZSETUP if and only if the file already exists in the database. Otherwise all new additions to the list will have the additional option of gaining descriptions from the Alternate. ++009++ You can tell DIZL to use ONLY the Alternate selection, and NOT look for descriptions inside archives at all. This is especially helpful for CD-ROM lists, because unarchiving descriptions from them is very time- consuming. You can use this option for Hard drive installations as well. ++010++ Adding Descriptions found in Alternate Description sources to the archives themselves can be accomplished with DIZL. Only files that do not already have one or more of the normal internal description files will be effected. No archives which have been Secured, passworded, etc, will be touched. And naturally CD-ROM files will not be affected. This setting can be enabled safely, since it is negated when one of the above situations occur during program runs. DIZL will create a FILE_ID.DIZ and a DESC.SDI file and during the scan process will import them to the archive, if possible. See the Toggles and Miscellanea Menu in DZSETUP. If you have SWAPPING turned on (at Toggles) then DIZL will swap most of itself out of memory for this procedure. THIS OPTION IS ONLY AVAILABLE TO REGISTERED USERS. ++011++ ┌─────────────────────────────┐ │ FILES.BBS Importing │ └─────────────────────────────┘ The format of the file is plain ascii text, with the filename beginning in column 1, one or more spaces, then the description of any length on one line up to 255 characters total, terminated with a LF/CR sequence. Some FILES.BBS formats include filesizes and/or dates. DIZL fully supports long-style FILES.BBS files also, which have the description extended to more than one line. You can specify the name of the FILES.BBS file, if different at the Descriptions menu in DZSETUP. You must have FBBS or ALL flagged before you will be able to change this setting. Additionally, you can specify at which COLUMN a "files.bbs" file's description begins on. This is necessary for the long-style, and helps to exclude extraneous information creeping into your list files. You will need to be familiar with the particular FILES.BBS you intend to import in order to accurately import the descriptions from them. ++012++ ┌─────────────────────────────┐ │ CD-ROM Installations │ └─────────────────────────────┘ The option "Notice CD-ROM Drives" can be used with Hard drive installations, but it will not process your datafiles completely, since files can be changed, or deleted from hard drives. This setting is mainly for situations where no additions or deletions can possibly occur, ie: CD-ROMS. This option will increase the speed at which DIZL will run, because with this setting many tasks that DIZL would normally need to take are skipped. This setting, if turned on, will override the Add-Diz-files flag. Mixed configurations, when some directories are on the Hard drive and others are on a CD-ROM, should have this setting disabled. You can change this setting at the Toggles menu in DZSETUP. ++013++ ┌────────────────────────────────┐ │ Excluding Files by Extension │ └────────────────────────────────┘ Updates to this string can be made in DZSETUP at the Miscellanea section. The string must be extensions separated by commas. For Example: BAK,ION,BBS No dots (.) should be included. Any file extension found in this string will not be processed by DIZL. Including hidden files, such as ION (4DOS "descript.ion" files) is safe and recommended. Up to 12 different extensions may be included. ++014++ ┌─────────────────────────────┐ │ Archiver Setup │ └─────────────────────────────┘ DIZL supports ARC, ARJ, ZIP, ZOO, RAR, LZH and SQZ archives completely. For the purpose of simplification and reliable performance, ARC files should have the programs ARCE.COM and ARCA.COM available to them. ARJ will need ARJ.EXE, ZIP will need both PKZIP.EXE and PKUNZIP.EXE, ZOO needs ZOO.EXE, RAR needs RAR.EXE, LZH needs LHA.EXE and SQZ needs SQZ.EXE. You do not have to have all the archivers for DIZL to function, but you do need at least two of them, and they must be available along your PATH. Each of these programs are copyrighted by their respective authors, agents and/or distributors. They are all available on most BBS systems in North America, and it is assumed you have at least two of them. The command-line parameters for the various Archivers, included as defaults for DIZL, do not have to be configured by you, but if they need adjusting for any reason, you may do so at Archivers Configuration in DZSETUP. Be aware that only the changes made to a particular configuration are used for that configuration. You can always revert to the original settings by pressing [F9] and saving your configuration. In the Archivers section, the command-lines include three "meta" strings which expand to either the default or configured strings you define. "%X" will expand to include the internal description files that will be extracted from each archive during program runs. "@A" will expand to the name of the effected archive, and "@F" will expand to the list of files to include in a created archive. Please note that "%X" will produce an error if it is included in a "Pack" command-line, and "@F" will cause problems if used in an "Unpack" command-line. ++015++ ┌─────────────────────────────┐ │ The Downloadable Archive │ └─────────────────────────────┘ List Configuration -> Downloadable Archive Configuration in DZSETUP handles these settings. Valid archivers are 1) what you have available and one of 2) ARC, ARJ, ZIP, ZOO, RAR, LZH, or SQZ. Because of the way the program functions - all archivers needed should be somewhere in your path. You also must specify the name of the archive to create. You do NOT have to use, for example, the extension ".ZIP" with the Archive Type ZIP, but is it highly recommended. You must specify a FULLY-QUALIFIED PATHNAME, or DIZL will likely produce an error when attempting to archive the lists. If you leave off the extension, the relative archiver's default extension will be used. DIZL will include a "file_id.diz" in your downloadable archive, if you create a file and include its name in this section of DZSETUP. Do NOT use the name "file_id.diz" here. DIZL will copy and rename whatever file you specify to the correct name just before archiving. DIZL will also allow you to include any other single file to your downloadable archive. Include its name at the Downloadable Archive menu in DZSETUP. If you are creating a Magic "Mini-List" you may also include its name here. You cannot use wildcards in this field. ++019++ ┌─────────────────────────────┐ │ Swapping for downloadables │ └─────────────────────────────┘ NOTE: The option for SWAPPING (at Toggles in DZSETUP) effects this part of DIZL. DIZL will swap most of itself out of memory when executing the external archiver command for the downloadable archive. SWAPPING effects Archiving the downloadable, or adding descriptions to archives. It will never swap when extracting internal description files. ++016++ ┌─────────────────────────────┐ │ MAGIC Names Annotated │ └─────────────────────────────┘ If you use a Magic-name file, DIZL can include a conspicuous notice in the main lists where the associated file is. If you have no Magic-File Name setup - anytime you try to configure a "Magic" setting dependant upon it in DZSETUP you will be prompted to enter the name of it. All other MAGIC file settings depend on this one. If you do not tell DIZL where the Magic-name file is, it will not be able to do much with it. NOTE: The FILES.BBS Style list does not Annotate Magic Names, even if you have it enabled. The FILES.BBS format does not, by nature, support this type of annotation. However, you may create a Magic Mini-List using the FILES.BBS style. ++017++ ┌─────────────────────────────┐ │ MAGIC "Mini-List" │ └─────────────────────────────┘ DIZL can create a "Mini" list with only the files listed which are in your Magic-Name file. This list will be created in addition to the other lists, using the same STYLE defined in the respective configuration. It will only use the files in the Magic-List which are also included in the particular configuration's database under which it runs. In addition to this, DIZL can create a separate Archive for just your Mini-List, else include it with your Regular Downloadable Archive above if its name is "included" in the archive. If you have DIZL create a separate archive for your "Majik" files, you will need to specify the Name of the archive to create (with fully-qualified path) as well as the List Archive Type setting for the Magic list. These all can be configured at the List Configuration Menu in DZSETUP. If you define the Mini-List's name in the File to Include, you must specify the fully qualified path-name - it is created in the DIZL home directory. You may also have DIZL create a separate archive and include it with the main archive also, by filling in all the "MAGIC" fields normally. You can specify a separate set of Header and Footer files to be used with the Mini-List as well. There is a separate Menu for the Header and Footer files under List Configuration. ++099++ ┌─────────────────────────────┐ │ Styles Configuration │ └─────────────────────────────┘ (See STYLES.DOC) ┌──────────────────────────────────────────────────────────────────────┐ │ COMMAND LINES ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────┘ DIZL defaults to update/creating lists using the INI file DIZLIST.INI. Key: DIZL /? for a summary of these commands. The "-" and "/" are equivalent switches. The Configurations: /C<filename> You can specify the configuration to use on the command- line using -C or /C. For example, to use your GAMEZ configuration, enter at DOS or from a batch file: "DIZL -cGAMEZ" (letter case doesn't matter). DIZL will expect to find and use GAMEZ.INI in the DIZL home directory. UNREGISTERED COPIES WILL ONLY USE DIZLIST.INI EVEN IF YOU DO PLACE A VALID INI FILE ON THE COMMAND-LINE WITH THIS OPTION. The Import Option: /I<filemask> This option tells DIZL to ignore the fact that <filemask> is already part of the database, and imports a description afresh from the Internal description files or Alternates. It simply updates the record in the database if it already exists, or adds it if it doesn't. This option will not allow a list to be created; it is simply for updating the database with up-to-date information. For example, you recieve a file called MYNETNFO.ZIP every week. The filename never changes - but the description might. Run DIZL /iMYNETNFO.ZIP to update this particular record. File masks are allowed as well, so DIZL -iMY*.ZIP works just as well, and it will update MYNETNFO.ZIP, MYNETFN.ZIP and MYNETNA.ZIP, for example. You can mix the /I command with /C command to update different databases. Do NOT include a path with the filename or wildcards, because DIZL's Database will know where to find them. Style Override: /S<style> You may at any time override the Style to create by including a valid choice on the command-line. See the STYLES.DOC file for the Proper names to use. If the name is invalid, the style configured for the list in DZSETUP will be used by default. ++018++ Database Packing: /PACK Pack runs automatically when n% of the files in the database are no longer somewhere in the database's configured directories. It could be triggered when you move n% of your files to a different *configured* directory as well. DIZL will re-import these descriptions as if new in a case such as this when DIZL runs under normal mode. You can configure the percentage at the Misc section of DZSETUP. The default is 8%. Purging the Database: /PURGE Purge is almost the same as Pack, but with one important difference. Pack removes records that no longer exist ON THE HARD DRIVE, from the database files. Purge removes records no longer CONFIGURED as part of the configured Paths. It also will remove non-existant files just like Pack does. Purge will never run automatically. If you remove a path from a configuration, it will not show up in the lists themselves, but the database files will retain all that data unused, until you run -PURGE. Purge should be run regularly, perhaps weekly or once or twice a month. *Notice* The Purge option also removes duplicated RECORDS from the database. This is not the same thing as Duplicated archives in your file libraries. If you notice a discrepancy in the total records reported in the Database Status after the Scanning process, and the number of records actually listed, then the Purge option will correct this. This can be caused during normal processing over a period of time, when duplicate files are deleted or removed automatically by other file processors; or, when two identical files are imported to different paths between DIZL runs so that DIZL processes them both as new files, and doesn't see them as duplicates until the following run. Command-Line parameters can be mixed and matched; If you need to Pack the GAMEZ database, you would enter "DIZL -pack -cGAMEZ". The order of the command-line parameters is not important. Purge and Pack do not (and should not) be run together. Purge does everything Pack does and more, so simply run Purge instead if and when needed. DZSETUP defaults to a Picklist of all *.INI files found. If none exist, as with new installations, you just start DZSETUP with DZSETUP DIZLIST to begin your primary configuration. Any time you need to create a new configuration, key in the name at the command-line for DZSETUP (Example: DZSETUP GAMEZ). ┌──────────────────────────────────────────────────────────────────────┐ │ SYSTEM REQUIRMENTS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────┘ The DiZList needs at least a 286 IBM-AT or compatible, and as much conventional memory as possible, depending primarily on how large a list is being made. It functions as a DOS program, and will run fine under OS/2 and Windows/Win95. It is safe to run in multi-tasking situations, and with Networks (Share should be loaded). DIZL may not function properly, and has not been tested, on the 8088 processor. DIZL and its associated programs have been made Multi-Tasker aware, and will give up time slices to the operating system. DIZL performs best when a disk cacheing program is loaded, such as SMARTDRV, Norton Cache, Hyperdisk, etc. Please allow at least 20 file handles (files=20) in your CONFIG.SYS file. If you do not run a disk cache program, the buffer setting should be at least 40, read ahead buffers set to about 4. (BUFFERS=40,4) All programs released with this package will use the current text mode, either 80x25, 80x43, 80x50, etc, Color or Monochrome; if your display equipment supports them. An EGA or better is recommended but not required; CGA monitors will function properly, however there is no code added to prevent "snow" from occuring. The PCX displays only on EGA or better monitors. If you use a CGA monitor with the Install program, you *will* see the fade-in/out, but without the PCX itself. The greatest advantage of a "real-mode" program such as this is compatibility with the 286 processor. However, DIZL will run in Virtual 8086 (Protected) mode (level 0 only). Desqview users will need to set aside a minimum of 400k system memory, Runs in background should be blank, Share CPU when foreground can be Yes, Swapping may be Yes, and Protection Level must be Zero. You may need to increase the memory requirements for larger lists. The program code and data will use 220k conventional memory. The 400k gives DIZL 180k of conventional memory to use for workspace and more may be required depending on the size lists you will be creating. If you have EMS/XMS/ VCPI/DPMI available, you should allow DIZL to use a minimum of 36k, more if possible. DIZL uses direct screen-writes at various times. Allow at least one text page. No graphics pages are needed. OS/2 users may run DIZL in a DOS session. Windows and WIN95 users may run DIZL in a DOS window. The same memory requirements mentioned in the paragraph above should be taken into consideration. DIZL is designed to be executed from the DOS command-line, specifically from a batchfile. There may be enough memory for DIZL to begin running, and later run out if the heap-space memory becomes too cramped to handle the list being created. DIZL has built-in error-controls available, and there should be no ill- effects if DIZL cannot completely process the list you have configured. Generally speaking, you will need 100k of heap-space for every 3200 files (32 bytes per file). This is in addition to the 220k needed for the program code and data image, for a total of approximately 520k conventional memory for approximately 9600 files. These are nominal figures and may vary depending upon memory fragmentation, etc. DIZL shells to call archiver programs for extraction and creation or updating archives. This process requires that the heap be freed for each and every call. Therefore, during the scanning process when new calls to the archivers occur most often, and during the final stage when archives are created, the index file resides solely on the hard-disk and is opened and searched there. This allows the heap to be safely released during calls to the archiver programs and reclaimed when DIZL regains control. Between these two steps of the program run, the index file takes up residence in heap-space, during the creation of the lists themselves. Swapping is not done during calls to archivers when extracting internal description files. If you have 480k or more conventional memory before starting DIZL, then all archivers will run in a shell without swapping for this type of process. Swapping is available, however, for creating the downloadable archives. It is usually only required when the list- file's size before compression is over 5 megabytes, dependent also upon memory availability. Swapping can be enabled in DZSETUP; see the Configuration Section above and DZSETUP.DOC for more information. If space is limited, but does not cause the error-controls in the program to trigger, you may see geometrical growth of the database files. 3200 files will require a main database file of a tad over 2 megs. If you notice the database file is exorbitantly large, then this condition has occured. The fix for this is to run "DIZL -Purge" and to make more conventional memory available, or remove a few of the configured director- ies from your configuration in order to make the list smaller. You should never have to delete the database files and start over; but this also works as a last resort. ┌──────────────────────────────────────────────────────────────────────┐ │ NEW VERSION UPDATES ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────┘ This version, version 1.4, fixes a bug with some archives which caused DIZL to hang while scanning the archive for description files. Thanks goes to Torsten Kilian of CCB-WORLD for reporting some errors which helped me solve the problems with version 1.20 and 1.30. Also much thanks to H. Bro-Nielsen for sending me an archive which was causing the problem. ┌──────────────────────────────────────────────────────────────────────┐ │ BETA TEAM ACKNOWLEDGEMENTS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────┘ From early 1996 until early fall, the Beta Team of The DiZList has been working to help bring you a reliable and useful program. Without their help, this program would be nothing like it is today. Instead, it would be full of bugs, hard to use, and fairly common-place at most. The Beta Team members as of version 61ß are: Name BBS name BBS number Fido Address -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Chris Bradley ThunderWare BBS 812-526-2629 1:231/1310 Jack Smith Ultratech 615-356-0453 1:116/30 (MAIL ONLY) Jeff Schrunk Ready Room CBIS 405-454-4825 1:19/153 Robert Kidwell The BORG 615-368-7003 1:116/52 (KIDWare) Gene Tucker Nobody Inn 615-781-9954 1:116/161 Heather Tucker " " " Matthew Seavey Isle of the Immortals 203-266-6079 1:141/1255 (node 1) 860-868-1445 1:141/1256 (node 2) Jon Parise Infinite Twilight 908-637-8243 1:2606/421 Tony Chatman Sorrow's Path 615-895-2151 Tom Brown Diamond's In the Rough 502-439-7904 1:3621/4 Kenneth Duke Super Systems 615-860-5604 1:116/157 (node 1) 615-860-5603 1:116/158 (ISDN) I want to extend my thanks to each and everyone, both old and new members, for their help. I have really worked overtime to please each of them, and as a result of that, the program will definately be worthwhile to each of you. By all means, if you have opportunity, contact them or their BBS and thank them for their help. You'll also be able to obtain the latest version of The DiZList from them, or from me. You may contact me at the below addresses. ┌──────────────────────────────────────────────────────────────────────┐ │ MIND OVER BYTE SOFTWARE is owned and operated by Mark Bloss, Sysop │ │ of A SPYER BBS, Nashville Tennessee, (615) 831-9284 (1:116/180) │ │ PO BOX 112015, Nashville Tennessee, 37222 │ └──────────────────────────────────────────────────────────────────────┘ Any distribution of this software MUST INCLUDE the original documentation (this file) and description information included in the FILE_ID.DIZ or other description file. DO NOT DISTRIBUTE THE EXECUTABLE FILE WITHOUT THE *ORIGINAL* ACCOMPANYING DOCUMENTATION. To do so is in violation of copyright laws. It is also illegal to distribute any copy of this program that has been re-engineered directly or indirectly in any way whatsoever by someone other than the original author or agents, whether or not the result is beneficial to the original author or agents, or end users. DISCLAIMER: There is no guarantee as to the fitness of this program for use on any machine for any purpose. The author cannot be responsible for damages that may occur from the use, or misuse, of this program. The _user_ of this program assumes all responsibility for protecting his or her data files and system from any damages that might occur, consequential or inconsequential. The author encourages you to test for virus infection and backup vital data before installing and executing any new software on your machine. ┌─────────────────────────────────────┐ │ MIND OVER BYTE SOFTWARE │ │ PO BOX 112015 │ │ Nashville, Tennessee │ │ 37222 │ │ BBS (615)831-9284 │ └─────────────────────────────────────┘ Please include with any correspondence the name of this program, the version number and where it was obtained. Acknowledgements: Some program source code was obtained from published public domain sources and some registered shareware sources, some of it altered for seamless performance in some or all the DIZL programs. Those who knowingly and unknowingly contributed to DIZL deserve my thanks, and the recognition. The names I know are, in no particular order, Joe McElmeel, Thomas Wagner, Gerhard Hoogterp, and a small portion of Turbo Technojock's Toolkit was used in the INSTALL program. Most of the code was written by the named author, and suggestions and ideas were acquired from other sources as well, including Sourceware Archival Group (SWAG) and the Pascal echos in Fido and 50H-Net. DIZL would be nothing like it is today however, without the fine Beta Team that found and reported bugs, made suggestions, and made a point to sustain my ego over the past several months. They are the real heroes, having put up with a few ruined archives along the way and the cost of long-distance charges which they all shared in at some time or other. And to think they started over on their databases more than once; it just amazes me that they were such good sports about it. And I can't thank them enough for their help! Credits: Turbo Technojock's Toolkit Copyright 1986-1993 TechnoJock Software, Inc. QEMM/Desqview Copyright (c) 1992-93 by Quarterdeck Office Systems IBM, PC-DOS, IBM-DOS, MS-DOS, OS/2, Windows,Windows95 etc. Copyright International Business Machines Corp 1981-1993+ Copyright Microsoft Corp 1981-1993+ CompSys/Oops (Compression Toolbox, G. Hoogterp) Copyright (C) 1994 LiveSystems ARC Copyright 1986-91 Vernon D. Buerg ARJ Copyright 1990-94 ARJ Software LHA (Lzh) Copyright Haruyasu Yoshizaki, 1988-1991 RAR Copyright 1993-96 Eugene Roshal SQZ Squeeze It, Copyright 1992, J.I. Hammarberg ZIP (PkZIP, PkUNZIP) PkWare Inc. Copyright 1989-1993 ZOO Copyright 1991, Rahul Dhesi NDOS (Norton Utilities-DOS shell) Copyright 1993 by Symantec Corporation 4DOS (DOS shell) Copyright 1988-95, Rexx Conn and J.P Software The DiZList, DZSetup, and the Install program Copyright 1996-97, Mind Over Byte Software {end}